or your short tag-based citation style?
> >
> > biblatex implements this with the "alphabetic" style. I'm not aware of
> > a specification, though. Does the "short" form in ConTeXt exist for a
> > specific reason? :)
> >
> &
mat in a bibliography. Currently,
> > > I'm using the aps style which fits so far, except of the plain number
> > > as reference. In concrete, I want to change the following:
> > > - Use the first letter of the last name and the year as reference
> > > (this should
a bibliography. Currently,
> > I'm using the aps style which fits so far, except of the plain number
> > as reference. In concrete, I want to change the following:
> > - Use the first letter of the last name and the year as reference
> > (this should be exactly the short
year as reference
> (this should be exactly the short form). It is more less also
> described here [1].
> - Highlight publications of a certain author with an extra char (e.g.
> '>')
>
> Here is a minimal example (lets assume, every occurrence of Knuth
> should be highlig
the short form). It is more less also described here [1].
- Highlight publications of a certain author with an extra char (e.g. '>')
Here is a minimal example (lets assume, every occurrence of Knuth should be
highlighted):
```
\setupinteraction[state=start]
\startbuffer[testdata]
@Book{knu
/ help
Command/ high
Command/ highlight
Command/ label
Command/ labellanguage
Command/ labeltext
Command/ labeltexts
Command/ language
Command/ leftlabeltext
Command/ linenote
Command/ low
Command/ lowhigh
Command/ lowmidhigh
Command/ margindata
Command/ mathcommand
Command/ mathdoubleextensible
Com
ct, thanks!
The "\definebar[...][inlined]" doesn't look quite right though -- the
issue that I'm having is that I can't figure out how to highlight across
both sides of an \alignhere without any questionable hacks. Unless the
new "inlined" does work across an \alignhere and I'm jus
!
>
> The "\definebar[...][inlined]" doesn't look quite right though -- the
> issue that I'm having is that I can't figure out how to highlight across
> both sides of an \alignhere without any questionable hacks. Unless the
> new "inlined" does work across an \alignhere an
having is that I can't figure out how to highlight across
both sides of an \alignhere without any questionable hacks. Unless the
new "inlined" does work across an \alignhere and I'm just not seeing it
in t
managed to find a "solution" for
this, although I'd prefer something a bit less hacky. Any ideas?
Also, is there a way to highlight an equation across an \alignhere? Once
again, I've found a "solution", but like before, it's pretty hacky.
Example files are attached.
the next
managed to find a "solution" for
this, although I'd prefer something a bit less hacky. Any ideas?
Also, is there a way to highlight an equation across an \alignhere? Once
again, I've found a "solution", but like before, it's pretty hacky.
Example files are attached.
maybe
ution" for
this, although I'd prefer something a bit less hacky. Any ideas?
Also, is there a way to highlight an equation across an \alignhere? Once
again, I've found a "solution", but like before, it's pretty hacky.
Example files are attached.
Thanks,
-- Max
\setupindenting[yes, 3em]
\setuphe
xt and
> makes Vim stay in Lua mode when it should go back to ConTeXt mode (I’m
> not too savvy of the details).
>
> The maintainer came up with a workaround [1] to force returning to
> ConTeXt mode, although the parenthesis remains highlighted as an error.
>
> That highli
as an error.
That highlight bothers me, so my own workaround is to copy the lua.vim
file in my own .vim/syntax folder and comment out the ‘syn match
luaParenError ")"’ line (l.61 in my Vim version).
Maybe playing with the ‘contained’ keyword (in lua.vim) could lead to a
proper solutio
...
Hope it helps
Christian
Am Sa., 6. Jan. 2024 um 13:04 Uhr schrieb Damien Thiriet via ntg-context <
ntg-context@ntg.nl>:
> Hello,
>
>
> Happy New Year!
>
> I got into a bug in my Vim syntax highlighting version.
> Highlight stays in lua mode after ctxlua macro is clo
Hello,
Happy New Year!
I got into a bug in my Vim syntax highlighting version.
Highlight stays in lua mode after ctxlua macro is closed.
Here is a MWE, where «this should not be highlitghted as
a comment indeed is.
\starttext
Hello!
\ctxlua{context("does the parser work?")}
-- t
is not interactive like it would
be if I used apa:cite:authoryear and just removed the parentheses in the
options. How do I get it to highlight blue and be interactive like the
default behaviour when you turn on interaction? Also this is probably
overkill so if there is a better way to achieve
It does not highlight e.g \starttext keyword by default. The colorscheme seems
adapted to LaTeX mode so I managed to fix this now for all \start - \stop
commands with this code put in ~/.emacs.d/init.el
(add-hook ’ConTeXt-mode-hook
(lambda ()
(font-lock-add-keywords nil
Am 19.07.23 um 15:38 schrieb Jan-Erik Hägglöf:
Dear All!
I've been using emacs AUCTEX for quite a while and found it very
convenient to work with.
One issue is the lack of syntax highlighting.
https://wiki.contextgarden.net/Text_Editors says, Emacs has ConTeXt
support including syntax
-lock-add-keywords nil
'(("\\(starttext\\)\\>" 1
font-lock-warning-face t)
("\\(stoptext\\)\\>" 1
font-lock-warning-face t)
and it seems to highlight the start-stop text keyword.
So my q
to highlight
source code. This already worked with HTML, LaTeX, and formats
like docx, and is now also supported for ConTeXt.
- *Inline code*: older versions of pandoc had some weird behavior
wrt inline code in ConTeXt, switching between `\type` and
`\mono`, which made it difficult to customize
.57895496379132
mkiv lua stats > v-node processing time: 1.464 seconds
mkiv lua stats > loaded tex modules: 10 requested, all found (*-filter
*-libs-imp-zint *-module-catcodes *-s-fonts-show *-s-symbols-show
*-scite *-syntax-groups *-syntax-highlight *-vim *-visual)
mkiv lua stats > l
h
> % !TEX useConTeXtSyncParser
>\setupsynctex[state=start, method=max]
>
> Syncing works well enough—though I can see no difference between method =min
> and method=max, both highlight only a few words and not the entire text to be
> synced, but perhaps my expectati
between method
=min and method=max, both highlight only a few words and not the entire
text to be synced, but perhaps my expectations are out of line.
When I have these lines at the top of a component file and typeset the
product file, I get a rootfile.synctex file, but syncing itself goes awry.
Nothing
wrap it or replace it with something that
> will highlight indexed items in the text where they occur, e.g. change their
> colour.
>
> I could do this with a global find and replace (across many files) to replace
> \index with \MyIndex, say, and then define a \MyIndex that understands
day, 4 September 2022 06:51
>
> My own fault for not thinking head :-) but I have a largeish text with a
> lot of \index{...} entries. To make life easier for the proofreader I would
> like to temporarily redefine \index to wrap it or replace it with something
> that will highlight indexed i
redefine \index to wrap it or replace it with something that will
highlight indexed items in the text where they occur, e.g. change their colour.
I could do this with a global find and replace (across many files) to replace
\index with \MyIndex, say, and then define a \MyIndex that understands
My own fault for not thinking head :-) but I have a largeish text with a lot of
\index{...} entries. To make life easier for the proofreader I would like to
temporarily redefine \index to wrap it or replace it with something that will
highlight indexed items in the text where they occur, e.g
t what struts, line
distances, spacing, either of not adapt to current situation, delayed vs
immediate inclusion, etc ... you can't have both worlds
if course you can make some macro (or define a highlight) and
Dear List,
the red highlight block in the following example is not covering the two
40pt characters:
\definetextbackground[important][frame=no,background=color,backgroundcolor=red]
\starttext
abc\important{123{\switchtobodyfont[40pt]45}xy}z
\stoptext
Is there an option that fixes this?
Thanks
low" and "complements to main flow"
in order to
- again help the reader to tidy up concepts / ideas
- highlight the fact that complements are usually used to enrich
the main flow with "non-linearity"
3/ clearly split "general/global" and "specific
low" and "complements to main flow"
in order to
- again help the reader to tidy up concepts / ideas
- highlight the fact that complements are usually used to enrich
the main flow with "non-linearity"
3/ clearly split "general/global" and "specific
ot;\boxframed{Box B}");
boxit.C("\boxframed{Box C}");
defaultdx := 0pt;
defaultdy := 0pt;
A.c = origin;
B.w - A.e = (1cm, 0);
0.5[ A.s, B.s ] - C.n = (0, 1cm);
stacking := 0;
drawunboxed(A,B,C);
stacking := 1;
drawarrow A.s +- C.w ;
drawarrow B.s +- C.e ;
rigin;
B.w - A.e = (1cm, 0);
0.5[ A.s, B.s ] - C.n = (0, 1cm);
draw image (drawunboxed(A,B,C)) withstacking 2;
drawarrow A.s +- C.w withstacking 3 ;
drawarrow B.s +- C.e withstacking 4 ;
newpath highlight;
highlight := (A.sw -- B.se -- B.ne -- A.nw) enlarged EmWidt
.5[ A.s, B.s ] - C.n = (0, 1cm);
draw image (drawunboxed(A,B,C)) withstacking 2;
drawarrow A.s +- C.w withstacking 3 ;
drawarrow B.s +- C.e withstacking 4 ;
newpath highlight;
highlight := (A.sw -- B.se -- B.ne -- A.nw) enlarged EmWidth;
fill highlight withcolor "dar
the diagram shown in page 1 of the attached PDF. Suppose I want to
"highlight" boxes A and B by drawing a square around them. That is easy; simply
determine the bounding box of A, B (I do that manually here), and expand it a bit and
draw it. Simple. See page 2.
Now, suppose I want to fill this h
the diagram shown in page 1 of the attached PDF. Suppose I want to
"highlight" boxes A and B by drawing a square around them. That is easy; simply
determine the bounding box of A, B (I do that manually here), and expand it a bit and
draw it. Simple. See page 2.
Now, suppose I want to fill this h
sider the diagram shown in page 1 of the attached PDF. Suppose I
want to "highlight" boxes A and B by drawing a square around them. That is
easy; simply determine the bounding box of A, B (I do that manually here), and
expand it a bit and draw it. Simple. See page 2.
Now, suppose I want to f
oading > Module Catcodes (ver: 2018.04.16)
close source> level 4, order 5, name
'/Users/me/Applications/context-osx-64/tex/texmf-modules/tex/context/third/filter/t-module-catcodes.mkiv'
close source> level 3, order 5, name
'/Users/me/Applications/context-osx-64/tex/texmf-m
to include a highlight definition with white font
on black background with an inframed, but that doesn't seem to work (in
my definitions that is)
___
If your question is of interest to others as well, please add
On 4/26/2021 10:25 AM, Floris van Manen wrote:
What is the easiest way, if possible, to highlight some sections of
verbatim text?
given:
\starttyping
one two three
four five six
seven eight nine
\stoptyping
i'd like to color the word 'five' in red, or italic.
\starttext
\starttyping[escape
What is the easiest way, if possible, to highlight some sections of
verbatim text?
given:
\starttyping
one two three
four five six
seven eight nine
\stoptyping
i'd like to color the word 'five' in red, or italic.
.Floris
Hi all,
When compiling the rules-mkiv.tex (context/sources/general/manuals/rules)
file, the highlight lines that use mp graphics are rendered in black instead of
the colour defined by the file. This is visible on the three test sentences on
the top of the third page "test test me and
active in its own way - and certainly acts as a visual
> highlight - just not quite what I was expecting. ;-)
Aditya
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : n
.. \stopHeading and for subsections, which is where I
first noticed it.)
It looks quite attractive in its own way - and certainly acts as a visual
highlight - just not quite what I was expecting. ;-)
version 2020.11.24 00:41
--
Bruce Horrocks
Hampshire, UK
schrieb Denis Maier:
Hi,
I prefer links to be styled as normal text, but I'd nevertheless to
highlight them somehow on screen. The LaTeX package Hyperref adds red
frames to clickable content. Is something like that possible with
ConTeXt?
Best,
Denis
Hi,
I prefer links to be styled as normal text, but I'd nevertheless to
highlight them somehow on screen. The LaTeX package Hyperref adds red
frames to clickable content. Is something like that possible with ConTeXt?
Best,
Denis
> Am 11.06.2020 um 13:41 schrieb Axel Kielhorn :
>
>> Am 09.06.2020 um 20:41 schrieb Wolfgang Schuster
>> :
>>
>> Use a textbackground to highlight parts of your text.
>>
>> \definetextbackground
>> [Highlight]
>> [frame=off,
>> bac
> Am 09.06.2020 um 20:41 schrieb Wolfgang Schuster
> :
>
> Use a textbackground to highlight parts of your text.
>
> \definetextbackground
> [Highlight]
> [frame=off,
> background=color,
> backgroundcolor=yellow]
>
> \starttext
>
> \m{1
background filled fully, but anyway - how about
usage of "bar" for this?
Use a textbackground to highlight parts of your text.
\definetextbackground
[Highlight]
[frame=off,
background=color,
backgroundcolor=yellow]
\starttext
\m{1 + 2 = \unit{3 kilo newton}}
\m{1 + 2 = \Highlig
Lua from TeX" and "Calling TeX from Lua"
> (section +links) in a same page
> - Tools:
>- segregate "core tools" and "additional tools"
>- highlight existence of mtxrun and context scripts pages
> - Remove former "manually made li
- rework the "Further reading section", add PDF links and so on
- Programming & DB:
- Gather "Calling Lua from TeX" and "Calling TeX from Lua"
(section +links) in a same page
- Tools:
- segregate "core tools" and "additional tools"
-
quot;, add PDF links and so on
- Programming & DB:
- Gather "Calling Lua from TeX" and "Calling TeX from Lua"
(section +links) in a same page
- Tools:
- segregate "core tools" and "additional tools"
- highlight existence of mtxrun and context sc
which can be used. Example:
\setupbuffer
[before=\blank\blackrule\startnarrower\BufferStyle,
after=\stopnarrower\blackrule\blank]
[...]
\definehighlight
[BufferStyle]
[style=smallitalic,
color=blue]
Use the highlight-environment or create a new startstop-environment to
apply style
erride these defaults by using ":highlight" commands
after sourcing the "syntax.vim" file."
All three `Function`, `Delimiter` and `String` are minor groups, so they get
mapped to the preferred groups, which are `Identifier`, `Special`, and
`Constant`, respectively. Mo
, then it is a bug. Could you
provide a complete MWE.
Please find a MWE at the bottom of this post.
The expected behaviour is that the keyword `function` in the JavaScript
snippet and `foobar` in the Ruby snippet should be colored and in
italics, as comments are. The respective Vim highlight groups
.
Please find a MWE at the bottom of this post.
The expected behaviour is that the keyword `function` in the JavaScript
snippet and `foobar` in the Ruby snippet should be colored and in
italics, as comments are. The respective Vim highlight groups are
`javaScriptFunction` and `rubyMethodName`, which
find a MWE at the bottom of this post.
The expected behaviour is that the keyword `function` in the JavaScript
snippet and `foobar` in the Ruby snippet should be colored and in
italics, as comments are. The respective Vim highlight groups are
`javaScriptFunction` and `rubyMethodName`, which b
,11pt]
\setupbodyfontenvironment[default][em=italic]
\showframe
\starttext
\input tufte
\quotation{We thrive in information||thick worlds} because of our
marvelous and everyday capacity to select, edit, single out,
structure, highlight, group, pair, merge, harmonize, synthesize,
focus
s do; try
switching the
commented lines and re-rendering.
The quotation dash itself only \emph{looks} as I want it; when I
highlight and
copy the text or export it to the \cap{XML} backend, it's still two
dashes next
to each other. Instead, I'd like it to be the Unicode bar U+2015.
I'm not
sur
switching the
commented lines and re-rendering.
The quotation dash itself only \emph{looks} as I want it; when I
highlight and
copy the text or export it to the \cap{XML} backend, it's still two
dashes next
to each other. Instead, I'd like it to be the Unicode bar U+2015. I'm not
sure if \TEX/\LUATE
ond being
non-breaking) while the others do.
The quotation dash itself only /looks/ as I want it; when I highlight and copy
the text or export it to the XML backend, it's still two dashes next to each
other. Instead, I'd like it to be the Unicode bar U+2015. I'm not sure if
TEX/LUATEX all
-> highlight color -> show border hover color
it badly interfering with these widgets ... there seems to be no way to
turn that off (forms made with acrobat suffer a bit less because they
use a funny mix of appearances and border settings and ... because they
make these buttons from dingb
Henning Hraban Ramm schrieb am 05.08.2019 um 15:10:
Of course the behaviour depends on the PDF viewer… :-(
In Acrobat Pro 9 the radiobuttons work while I highlight form fields; if I
switch that off, all options are checked.
In Adobe Reader DC you can’t switch off form field highlighting
Of course the behaviour depends on the PDF viewer… :-(
In Acrobat Pro 9 the radiobuttons work while I highlight form fields; if I
switch that off, all options are checked.
In Adobe Reader DC you can’t switch off form field highlighting.
Preview.app only highlights on mouseover and checks all
P (or for other programming languages)
# ># >available.
# >#
# ># 1. Use the scite module which provides additional styles (e.g. cpp
# ># or json) but php is still missing.
# >#
# ># 2. Use Aditya's vim module which uses vim to highlight source code.
# >#
# ># Wolfgang
# &
other programming languages)
# ># >available.
# ># # 1. Use the scite module which provides additional styles (e.g.
# >cpp
# ># or json) but php is still missing.
# ># # 2. Use Aditya's vim module which uses vim to highlight source
# >code.
# ># # Wolfgang
# >
# >Maybe
# or json) but php is still missing.
#
# 2. Use Aditya's vim module which uses vim to highlight source code.
#
# Wolfgang
Maybe it is a misunderstanding but how can use these modules
in ConTeXt? I had in mind typesetting the code in ConTeXt
like \startTEX etc.
1. Scite module
\usemodule [scite]
\st
n) but php is still missing.
#
# 2. Use Aditya's vim module which uses vim to highlight source code.
#
# Wolfgang
Maybe it is a misunderstanding but how can use these modules
in ConTeXt? I had in mind typesetting the code in ConTeXt
like \startTEX etc.
Here is an example with the
e Aditya's vim module which uses vim to highlight source code.
#
# Wolfgang
Maybe it is a misunderstanding but how can use these modules
in ConTeXt? I had in mind typesetting the code in ConTeXt
like \startTEX etc.
Tomáš
_
for PHP (or for other programming languages)
available.
1. Use the scite module which provides additional styles (e.g. cpp or
json) but php is still missing.
2. Use Aditya's vim module which uses vim to highlight source code.
Wolfgang
also keep the hexagonal shape,
associating chemistry; and it would also indicate or highlight relation to "TeX".
But keep my notion or feeling just personal; the new logo is "nice enough" as
published on wiki.
Best regards,
Lukas
On Tue, 29 Jan 2019 19:58:40 +0100, Paul Schalck
Rik Kabel schrieb am 04.10.18 um 00:01:
List,
With recent betas, since a fix for tagged elements in tables, underbar
processing seems to have changed (or perhaps I just noticed it after
that fix).
Previously, the following highlight definition worked for both pdf and
export outputs
List,
With recent betas, since a fix for tagged elements in tables, underbar
processing seems to have changed (or perhaps I just noticed it after
that fix).
Previously, the following highlight definition worked for both pdf and
export outputs:
\definehighlight [Term][style={{\underbar
Hello list,
Do you know what should I add to my ftplugin/context.vim to have
\page highlighted when using ViM ?
I tried to understand context.vim color syntax but this is magic to me
(mapping is ok, but offtopic).
Thanks,
Damien Thiriet
on 1.08.0 (tex live 2018)
> > mkiv lua stats > control sequences: 46536 of 65536 + 10
> > mkiv lua stats > lua properties: engine: lua 5.3, used memory: 86 MB
> (ctx:
> > 85 MB), hash type: lua, hash chars: min(64,40), symbol mask: utf (τεχ)
> > mkiv
ou could mess it up, so be careful.
> ;; Your init file should contain only one such instance.
> ;; If there is more than one, they won't work right.
> '(ConTeXt-Mark-version "IV")
> '(ConTeXt-engine "luatex")
> '(TeX-command-extra-options "-shell-escap
e, they won't work right.
)
;; SERVER Download (MELPA):
(when (>= emacs-major-version 24)
(require 'package)
(add-to-list
'package-archives
'("melpa" . "http://melpa.org/packages/;)
t))
(eval-after-load "context"
'(setq TeX-command-list
(cons '(
; Your init file should contain only one such instance.
> >> > ;; If there is more than one, they won't work right.
> >> > '(ConTeXt-Mark-version "IV")
> >> > '(ConTeXt-engine "luatex")
> >>
won't work right.
>> > )
>> >
>> > ;; SERVER Download (MELPA):
>> > (when (>= emacs-major-version 24)
>> > (require 'package)
>> > (add-to-list
>> > 'package-
PATH" t)
> >
> >
> > (setq ConTeXt-mode-hook
> > (lambda () (setq TeX-command-extra-options "--purgeall")))
> >
> > (setq-default cursor-type 'bar)
> >
> > (set-curs
, but it is not an
acceptable replacement for font switches with pdf output. And since
the syntax for highlights ( \highlight{text} ) differs from that for
font switches ( {\highlight text} ), it is not simply a matter of
different environments for each output format, although perhaps
\groupedcommand
al bibliographies or xml input yet, but I guess you
> > can change the setup to use those.
>
> \definehighlight does not (by default) nest. You can handle this to
> some degree in css or xslt for XML exports, but it is not an
> acceptable replacement for font switches wit
for font switches with pdf output. And since the syntax for
highlights ( \highlight{text} ) differs from that for font switches (
{\highlight text} ), it is not simply a matter of different environments
for each output format, although perhaps \groupedcommand might help (I
have not tried
the syntax for
highlights ( \highlight{text} ) differs from that for font switches (
{\highlight text} ), it is not simply a matter of different environments
for each output format, although perhaps \groupedcommand might help (I
have not tried this).
But that is in some ways beside the point
On 7/18/2018 10:56, Hans Hagen wrote:
On 7/18/2018 4:59 AM, Rik Kabel wrote:
List,
Another oddity with elements in XML / xhtml / html export:
With a defined highlight, a break is inserted if the highlight is the
first item in an environment. If it is not the first item in the
environment
On 7/18/2018 4:59 AM, Rik Kabel wrote:
List,
Another oddity with elements in XML / xhtml / html export:
With a defined highlight, a break is inserted if the highlight is the
first item in an environment. If it is not the first item in the
environment, no break is inserted.
Most
On 7/18/2018 4:59 AM, Rik Kabel wrote:
List,
Another oddity with elements in XML / xhtml / html export:
With a defined highlight, a break is inserted if the highlight is the
first item in an environment. If it is not the first item in the
environment, no break is inserted.
Most
List,
Another oddity with elements in XML / xhtml / html export:
With a defined highlight, a break is inserted if the highlight is the
first item in an environment. If it is not the first item in the
environment, no break is inserted.
Most of the other odd breaks can be dealt with in css
and is sorted unter the normal main entry, if there doesn’t exist a
normal entry with the same subentry.
(These are just observations, I wouldn’t know how it should be different.)
But: Is there a way to highlight just subentries?
e.g. \index{Sun+emph->rays}
"""
\defineprocessor[
ucture, but you can
just use highlights and such as these get tagged (with classes) so one
then can relate them to e.g. fonts or colors. Keep in mind that \bf is
not a construct, but a highlight named 'important' is. We can't make
structure from non-structure.
(FWIW: as long as we don't have pr
reate a new
command/environment
with \definestartstop you get additional commands for the instance where
the space
at the begin of the environment are gobbled.
\definestartstop[Highlight][style=italic,color=red]
\starttext
Text \Highlight{Text} Text
\blank
\input ward\par
\startHighlight
\input
) two reasons for that:
- I’m the only user who asked for this (too much trouble for a single user).
- Easier alternatives would be to improve the ConTeXt core or the
context-highlight module.
It isn't too difficult to support this. See attached file.
This will clutter your PWD with temp files
On 12/21/2017 10:16 PM, Christoph Reller wrote:
>
> My module does not come in standard context. You have to download it
> from https://bitbucket.org/philexander/context-highlight. If general
> interest is high enough I can ask to
> add it.
Christoph,
could you enable issues in
:16 AM, Pablo Rodriguez <oi...@gmx.es> wrote:
>
> On 12/21/2017 05:04 PM, Christoph Reller wrote:
>> Dear Pablo,
>>
>> At least for XML you could use my module highlight-xml:
>>
>> \usemodule[highlight-xml]
>> \definetype[xml][option=xml]
>> [
o reasons for that:
- I’m the only user who asked for this (too much trouble for a single user).
- Easier alternatives would be to improve the ConTeXt core or the
context-highlight module.
Many thanks for your help again,
Pablo
--
http://www
t XML comments are colored the same way with your module
>> and with standard ConTeXt.
>
> That should not be the case. Could it be, that the highlight-xml
> module fails to load? Please check your log file for a "module not
> found" entry. I have attached the result
On Thu, 21 Dec 2017 21:16:45 +0100, Pablo Rodriguez <oi...@gmx.es> wrote:
> On 12/21/2017 05:04 PM, Christoph Reller wrote:
>> Dear Pablo,
>>
>> At least for XML you could use my module highlight-xml:
>>
>> \usemodule[highlight-xml]
>> \definetyp
On 12/21/2017 05:04 PM, Christoph Reller wrote:
> Dear Pablo,
>
> At least for XML you could use my module highlight-xml:
>
> \usemodule[highlight-xml]
> \definetype[xml][option=xml]
> [...]
> Note that even partial XML is highlighted correctly.
Dear Christoph,
many than
--this is a comment
> \stopLUA
> \stopTEXpage
> \stoptext
>
> Would it be possible that all comments in type and typing (at least, for
> Lua, XML and TeX) would have the same formatting for the whole comment
> contents, including the comment signs?
Dear Pablo,
At least f
1 - 100 of 318 matches
Mail list logo
